Repository navigation
SPSUpdate: Release packaging 4.4.0 (GA) - #75
Merged
Merged
Conversation
Backport the #59, #64 and #68 fixes (shipped on the 5.x line in v5.2.0) to the 4.x maintenance line (SharePoint Server 2016 / 2019 / Subscription Edition). - Manifest ModuleVersion 5.0.1 -> 4.4.0 (stable, no Prerelease marker). - Reconcile CHANGELOG: restore the [4.3.0] section (its packaging commit was never remerged into support/4.x) and promote the new entries to [4.4.0]. - Replace RELEASE-NOTES.md with the 4.4.0 GA section used as the release body, keeping the SharePoint 2016/2019 end-of-support notice. Co-authored-by: Copilot <[email protected]>
Pester Test Results 1 files 47 suites 10s ⏱️ Results for commit e061d0e. ♻️ This comment has been updated with latest results. |
….0.0) The assertion required ModuleVersion >= 5.0.0, a 5.x-line floor that leaked onto the 4.x maintenance line. It only passed on 4.x because the manifest was stuck at 5.0.1 (the 4.3.0 packaging commit was never remerged); bumping to 4.4.0 exposed it. Co-authored-by: Copilot <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
Release packaging for SPSUpdate 4.4.0 (GA) on the
4.xmaintenance line (SharePoint Server 2016 / 2019 / Subscription Edition). This ships the three fixes backported in #74 — already live on the5.xline in v5.2.0.ModuleVersion5.0.1 → 4.4.0 (stable, no Prerelease marker).[4.3.0]section is restored (its own packaging commit6e148e7was tagged asv4.3.0but never remerged intosupport/4.x, so the manifest was stuck at5.0.1and the 4.3.0 entries were still sitting under[Unreleased]). The new Refresh the live Patch Status on the Binaries card after ProductUpdate installs a CU #59 / Run the reboot-confirm boot task as SYSTEM instead of the stored farm credential #64 / Reconcile a deferred reboot already performed out-of-band (manual / Windows Update) #68 entries are promoted to[4.4.0];[Unreleased]is emptied.RELEASE-NOTES.mdreplaced with the 4.4.0 GA section used verbatim as the GitHub Release body, keeping the SharePoint 2016/2019 end-of-support notice.Contents of 4.4.0:
NT AUTHORITY\SYSTEM(-RunAsSystem), no stored-credential dependency.Excludes the held #71 fix (PR #72, DRAFT) — not yet validated at a CU.
Validated: PSSA 0 warning/error, Pester 298/0/1 on the backport branch (identical code).
This Pull Request (PR) fixes the following issues
None (release packaging; the shipped fixes #59/#64/#68 were closed by #67/#66/#69 and backported in #74).
Task list
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).